Method of, and system for, webcasting with just-in-time resource provisioning, automated telephone signal acquisition and streaming, and fully-automated event archival

ABSTRACT

A multimedia business communications platform enables conference casting over a network. End users or so-called “audience members” participate in conference casts from anywhere on the Internet or behind an enterprise firewall using a standard Web browser running a streaming media player. The conference platform typically includes a number of subsystems: a Web reservation subsystem, a voice server subsystem, a content storage subsystem, a monitoring data subsystem, an attendee access subsystem, and an archive subsystem. Web reservation subsystem provides a mechanism that enables an entity to make an event reservation. Web reservation subsystem typically includes a database and an associated database management system. Voice server subsystem validates a user and converts an incoming telephone signal (i.e., the conference call) to an output data stream. Attendee access subsystem responds to attendee requests and returns information (e.g., a data structure such as a stream metafile) that directs an attendee&#39;s streaming media player on how to join the conference cast. Content storage subsystem is used to manage event information and, under the control of the archive subsystem, to archive the event files. The monitoring data subsystem comprises a set of monitoring agents distributed throughout the network. Using these components, the system implements just-in-time resource provisioning, automated signal acquisition and streaming, and automated archiving upon event completion.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates generally to network-based conferencecalling whereby audience members access audio conference calls overcomputer networks, e.g., using computers running a Web browserprovisioned with a streaming media player.

2. Description of the Related Art

It is known in the prior art to provide a multimedia businesscommunications platform that transforms audio and video conferencinginto interactive conference casts with integrated streaming audio andvideo. End-users participate in conference casts from anywhere on theInternet using just a standard web browser, with the call being“streamed” to the participant. Streaming media, as is known, is a typeof Internet content that has the important characteristic of being ableto be played while still in the process of being downloaded. A clientmachine can play the first packet of an audio or video stream,decompress the second, while receiving the third. Thus, an end user canstart hearing/seeing the multimedia without waiting until the end oftransmission. Streaming media quality varies widely according to thetype of media being delivered, the speed of the user's Internetconnection, network conditions, the bit rate at which the content isencoded, and the format used. Non-streaming content is standards-basedin the sense that the server and client software developed by differentvendors, such as Apache server, Microsoft Internet Explorer, NetscapeNavigator, and the like, generally work well together. Streaming media,however, usually relies on proprietary server and client software. Theserver, client, production and encoding tools developed by a streamingsoftware vendor are collectively referred to as a format. Streamingmedia encoded in a particular format must be served by that format'smedia server and replayed by that format's client. Streaming mediaclients are often called players, and typically they exist as plug-insto Web browsers. The most common streaming formats are Windows Media(WMS), Real and Apple QuickTime.

A conference call event typically is set up as illustrated in FIG. 1 andas described below. A host 100 contacts a service bureau 102 to schedulea conference event. The service bureau typically operates an eventregistration system 104. At step (1), the host 100 calls a Webreservation specialist. At step (2), the reservation specialist createsa customer account if one does not already exist and schedules aconference event. At step (3), the specialist enters the eventinformation into the event registration system 104. Then, at step (4),the specialist confirms the information and sends the host 100 thefollowing: audience Web site address, host Web site address, an eventidentifier and a user name and password. At step (5), the host 100enters the host Web site address and obtains a host login page. The hostenters the event identifier, user name (if required) and password (ifrequired) provided by the reservation specialist at the service bureau.At step (6), the host 100 accesses an administration page. From there,he or she can carry out a number of provisioning and management taskssuch as: provisioning and sending invitations to the audience members,monitoring the event, accessing an archive of the event if available,editing the archive, accessing usage reports, accessing eventinformation, and editing event information. At step (7), the host sendsthe invitations to the audience members. The message typically includesthe event identifier, as well as a link to an audience Web site. At step(8), the prospective audience members receive the notification from thehost. To access the event, an audience member clicks on the link (orenters a URL manually) to launch his or her browser's media player tothe audience Web site. To connect to an event, an end user audiencemember needs to have a computer with a video card (standard in allcomputers), sound card and Internet connection, an Internet browser(Internet Explorer or Netscape Navigator, or the like), streaming mediaplayer (e.g., Windows Media Player, RealPlayer or the like) and the Website address of the event. From the audience Web site, the audiencemember enters the eventID, user name (if required) and password (ifrequired) to access the event. Of course, one or more of theabove-described steps can be carried out automatically and/or in anonline manner.

Traditional Internet conferencing casting systems have severaldeficiencies. These applications typically use databases to generatereservation information, to initiate events, and to authenticate a hostor the attendees. The database dependency creates a potential singlepoint of failure because if the database is unavailable, events cannotbe run. Likewise, a typical application runs the event streams from asingle server, which again represents a single point of failure andlimits scalability, i.e., the number of attendees that can attend theconference. Moreover, the prior art systems require advanced setup forthe streams, which dictates a blackout period between the time that anevent is reserved and the occurrence of the event itself. Thus, once anevent is scheduled, a service provider typically must provision orallocate in advance various system and other resources. Such resourcesinclude, without limitation, media encoders, storage, networkconnectivity, streaming server ports or publishing points, and the like.This is in addition to the human resources required to handlereservations and to provide administrative functions. As a consequence,prior art conference casting systems do not have the capability ofreserving and then immediately executing the event, with the resultingstream being immediately available to an audience member. In prior artsystems, stream redundancy typically requires special handling andraises costs. Prior art conference casting systems also do not have thecapability to archive the event in an automated manner and/or to managewhen particular streams get interrupted before the event is terminated.

These and other problems of the prior art are addressed by the presentinvention.

BRIEF SUMMARY OF THE INVENTION

The present invention implements a system for network-based conferencecalling that provides a comprehensive set of functionality forinteractive communication services and is designed for maximumscalability and reliability. The system provides “just-in-time” oron-demand resource provisioning and automated telephone signalacquisition and streaming. An entity makes a reservation for an eventand receives an event identifier and an access code or PIN. Informationabout the event (such as desired stream format, archive time period, andthe like) preferably is stored on a content storage subsystem and alsoasynchronously in a traditional relational database. When a user (thehost or an entity acting on the host's behalf) then initiates a call (ordual calls for redundancy) by entering a telephone number, the call isrouted to an available voice center and automatically streamed in one ormore stream formats, preferably over a content delivery network. A voiceserver validates the event PIN preferably without access to the contentstorage subsystem or the database. The late binding of the call to anavailable resource, and the ability of the voice server to validate anevent PIN without use of any external subsystems, provides for a highlyreliable and scalable system. The audience members are provided with alink (an attendee URL) that preferably self contains all the necessaryinformation to give access to the stream, again without reliance on thecontent storage subsystem or database. The audience members use theirweb browsers and associated media players to listen to the stream live.After the call is disconnected, an archive is generated from the datastream file copies that were uploaded from the voice server(s) to thecontent storage subsystem during the call. The archive preferably ismade available for audience members for a length of time specified atreservation time.

The conference call system of the invention does not requirepre-provisioning of physical resources. Rather, substantially allresources are automatically bound to the event upon user call-in. Theseresources include the data center, voice server and the encoder. This“just-in-time” or on-demand allocation of audio resources enables thesystem to become more fault-tolerant. If any resource or asset failsprior to signal acquisition, that equipment is removed from an availableresource pool. This allows the system to choose among assets that areavailable and in working order. To ensure that the state of these assetsis correct, the system implements automatic monitoring and testing ofresource assets. A dial-in results in the conference using onlyresources that are working, thus maximizing fault tolerance. After auser logs in and is connected to a voice server, the system also doesnot rely on a database to authenticate access and initiate the event.The database interface of the system preferably is asynchronous, suchthat if the database is unavailable at the time a request for an eventreservation is made, the reservation completes as required. Later, thedatabase is updated with the reservation information for reportingpurposes. The event can be executed even if the database has not yetbeen updated or is unavailable.

In one particular embodiment, the present invention implements amultimedia business communications platform that enables conferencecasting over a network. End users or so-called “audience members”participate in conference casts from anywhere on the Internet or behindan enterprise firewall using a standard Web browser running a streamingmedia player. The conference platform typically includes a number ofsubsystems: a Web reservation subsystem, a voice server subsystem, acontent storage subsystem, a monitoring data subsystem, an attendeeaccess subsystem, and an archive subsystem. Web reservation subsystemprovides a mechanism that enables an entity to make an eventreservation. Web reservation subsystem typically includes a database andan associated database management system. Voice server subsystemvalidates a user and converts an incoming telephone signal (i.e., theconference call) to an output data stream. Attendee access subsystemresponds to attendee requests and returns information (e.g., a datastructure such as a stream metafile) that directs an attendee'sstreaming media player on how to join the conference cast. Contentstorage subsystem is used to manage event information and, under thecontrol of the archive subsystem, to archive the event files. Themonitoring data subsystem comprises a set of monitoring agentsdistributed throughout the network. By leveraging these components, thesystem implements just-in-time resource provisioning, automated signalacquisition and streaming, and automated archiving upon eventcompletion.

The foregoing has outlined some of the more pertinent objects andfeatures of the present invention. These objects should be construed tobe merely illustrative of some of the more prominent features andapplications of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and theadvantages thereof, reference should be made to the following DetailedDescription taken in connection with the accompanying drawings, inwhich:

FIG. 1 is a conference casting system of the prior art illustrating howa host makes an Internet audio conference reservation;

FIG. 2 is a block diagram illustrating the various functional subsystemsthat comprise the conference system of the present invention;

FIG. 3 is an illustrative fill-in form used by the Web reservationsubsystem to create a conference event reservation;

FIG. 4 is a block diagram of an illustrative voice server subsystem ofthe present invention;

FIG. 5 is a block diagram of an illustrative voice server;

FIG. 6 is a simplified flowchart of the operation of the voice serverupon initiation of a conference call;

FIG. 7 is a flowchart illustrating how an audience member joins theconference event;

FIG. 8 is a block diagram of the components used to enable an audiencemember to join the conference event as described in the flowchart ofFIG. 7;

FIG. 9 is a flowchart illustrating an automated archiving functionaccording to the present invention; and

FIG. 10 is a representative stream “reflector” network that may be usedto deliver the conference streams.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The present invention implements a multimedia business communicationsplatform that enables conference casting over a network including,without limitation, the publicly-routable Internet, a corporateintranet, a private network, or any combination thereof. End users orso-called “audience members” participate in conference casts fromanywhere on the Internet or behind an enterprise firewall using astandard Web browser running a streaming media player. The conferenceplatform described herein enables the rapid deployment of services thatcan be easily integrated into any web application. As seen in FIG. 2,the platform 200 provides and/or interfaces with a number of subsystems:a Web reservation subsystem 202, a voice server subsystem 204, a contentstorage subsystem 206, a monitoring data subsystem 208, an attendeeaccess subsystem 210, and an archive subsystem 212. Typically, eachsubsystem is implemented as computer software, or a combination ofsoftware executing on computer hardware. Web reservation subsystem 202provides a mechanism that enables an entity 212 to make an eventreservation, typically by connecting to the Web reservation subsystem202, preferably over a secure link 214 such as HTTPS, a VPN, or thelike. Web reservation subsystem 202 typically includes a database 203and an associated database management system 205 (e.g., Oracle, IBMDB/2, or the like) for managing and updating of reservation data. Voiceserver subsystem 204 validates a user and converts the incomingtelephone signal (i.e., the conference call) to an output data stream.Attendee access subsystem 210 responds to attendee requests and returnsinformation (e.g., a data structure such as a stream metafile) thatdirects an attendee's streaming media player on how to join theconference cast. Content storage subsystem 208 is used to manage eventinformation and, under the control of the archive subsystem 212, toarchive the event files. The monitoring data subsystem preferablycomprises monitoring agents implemented in software executing onmachines distributed throughout the network. As described below, eachvoice server subsystem (and there may be multiple ones) have a set ofvoice servers, as will be described in more detail below. The monitoringagents collect data from the servers in the voice server subsystem(s)and, in particular, data about what streams are active and at what portsor publishing points.

Entity 212 typically accesses the Web reservation subsystem 202 byopening a Web browser to a given URL, which, by way of example only, isillustrated as https://web.servicebureau.net/make_reservation.jsp.Preferably, the Web reservation, attendee access and archive subsystemsare available at a mirrored site. In such case, a traffic manager 216 isused to direct the entity to an optimally located (e.g., in terms ofload, network traffic and/or latency) subsystem. Traffic managementproducts and services are known in the art. An illustrative system isknown commercially as FirstPoint^(SM) and is available from AkamaiTechnologies of Cambridge, Mass. The FirstPoint technique is describedin commonly owned, U.S. Pat. No. 7,111,061. Other commercially availableglobal routing products include Cisco Global Director, global loadbalancers from F5, and the like. Any product/system/managed service thathas the ability to direct a client request to one of a set of mirroredsites based on network traffic conditions, server load, and the like,may be used in the present invention to connect an entity to themirrored subsystem.

Generalizing, the platform 200 typically is a set of computers. Arepresentative machine is a server running commodity (e.g.Pentium-class) hardware, an operating system (e.g., Linux, Windows 2000,or the like), an application runtime environment (e.g., Java), a Webserver (e.g., Apache), and a set of processes (e.g., Java servlets,linkable libraries, or the like, depending on platform) that provide thefunctionality of a given subsystem. Thus, for example, the Webreservation subsystem 202 is implemented as a Java servlet that presentsa fill-in form to the entity, receives data input by the entity, andcreates an event reservation for an Internet conference cast event. Webreservation data is stored in database 203 under the control of thedatabase management system 205.

FIG. 3 illustrates a representative fill-in form 300 that is presentedto the reserving entity (a “reservationist”), preferably online via aWeb browser. The form 300 guides the entity to identify the streamingmedia format 302 (e.g., Real, Windows Media, Quicktime), a securitylevel 304, and to provide an on-demand availability designation 306, thelatter information being selected from a listbox identifying how longthe event should be archived. The entity fills in the form, perhaps inan automated manner. The reservation subsystem (e.g., a servlet)generates a unique event ID, an access code or PIN, and an attendee Website address (an “attendee URL”), which information is then stored in adata file 308. Preferably, the data file is in XML format and has anappropriate identifier, e.g., event_info.xml. The event_info.xml datafile preferably comprises given information including, withoutlimitation, event title, format, time, eventID, PIN, attendee URL,status (e.g., reserved, completed, or the like). As noted above, the PINis an access code that is used by a conference host to initiate (orrestart) the conference. Typically, the conference host is a servicebureau employee, a person running the conference, or, more generally,any other person, process or automated routine.

In a representative embodiment, the Web reservation subsystem 202instantiates a process (e.g., a servlet) for each event reservation.This servlet generates the event_info.xml file and returns giveninformation to the entity requesting the event. In particular,preferably the servlet returns to the entity a data file comprising aneventID, a host access code or PIN, and an attendee URL. Thereafter, theentity forwards the attendee URL to each prospective attendee, e.g., bye-mail, by publishing the attendee URL in an identifiable location, bysyndicating the information to other web sites that providenotification, and the like. A representative attendee URL may be of thefollowing, illustrative only, format:

https://web.servicebureau.net/meta?event=<eventID>&format=<name>.

As can be seen, preferably the attendee URL has enough embeddedinformation about the event to enable the attendee to attend an event,even (as will be described) if the content storage subsystem isunavailable. As will be described below, when an attendee (i.e., anentity that desires to attend the event) activates this URL, theattendee's streaming media player will be directed to a given URLgenerated by the attendee access subsystem 210. In addition toforwarding the data file to the reserving entity, the servlet forwardsthe event_info.xml file to the content storage subsystem 204 and to thedatabase management system 205. The event_info.xml data file preferablycomprises given information including, without limitation, event title,format, time, eventID, PIN, attendee URL, and status (e.g., reserved,completed, or the like). Content storage subsystem 204 preferably alsois mirrored, in which case traffic manager 216 is again used todetermine which content storage subsystem should handle the request.When the event_info.xml file is received at the content storagesubsystem 204, the subsystem provisions a directory named by theeventID. The event_info.xml file and event archive files (describedbelow) are stored in the <eventID>directory. Setting up this directoryin the content storage subsystem is the only resource allocationrequired at the time of the event reservation.

A significant technical advantage of the system is that pre-provisioningof physical resources is not required and that substantially allresources are bound to the event upon user call-in as opposed to duringthe reservation process itself. These physical resources, as will bedescribed, include the data center at which the voice server subsystemis hosted, the voice servers in the subsystems, the encoders running ona given voice server, and the like. In particular, unlike the prior art,the inventive system does not require that physical resources bereserved ahead of time. An event can be reserved and then executedimmediately thereafter (provided the attendee URL is disseminated), andall physical resources are then allocated to the event in a“just-in-time” (JIT), on-demand fashion. Unlike the prior art, an entity(e.g., a person, an automated process, or the like) making a reservationmay reserve an event for any time, as long as the scheduled time is notin the past. Preferably, any “scheduled” time for the event is notenforced, but rather it is used only as a guideline. In addition,preferably there are no restrictions on how “late” the event isconducted.

A voice server subsystem 206 preferably is accessible from multiple datacenter locations. According to a technical advantage of the invention,telephone signal acquisition occurs in an “automated” manner in that thesystem does not need to pre-provision resources with respect to a givenevent. In a representative embodiment, audio signal acquisition isaccomplished through any number of well-known mechanisms. Thus, forexample, an 800 number system having advanced routing features may beused to route the call to one of a set of geographically dispersed datacenters. Such routing capabilities are known in the art. In such case, asingle “800” telephone number would be used for all voice serversubsystems and all voice servers in the system. Alternatively, a singlededicated telephone number may be used for each voice server subsystem,e.g., an 1-858-xxx-yyyy number for a data center (and the associatedvoice server subsystem) located in San Diego and an 1-408-xxx-yyyynumber for a data center (and its associated voice server subsystem)located in Philadelphia. In the latter case, the single telephone numberrepresents all of the voice servers at the particular voice serversubsystem data center location. Two or more separate telephone numbersare useful in the system where it is desired to provide a conferencebridge for the call, so that multiple parties can be involved. A bridgedconference call would thus be processed in two voice server subsystems,thus creating multiple (i.e., redundant) streams for the conference.This is often advantageous during the archiving process as will be seenbelow.

Generalizing, preferably data centers are geographically diverse toguard against natural disaster, and each data center hosts a voiceserver subsystem 206. As illustrated in FIG. 4, a representative voiceserver subsystem 400 comprises a set of one or more voice servers 402a-n that are connected to a front-end telephone switch 404 (e.g., AT&T5ESS, Nortel DMS 100, or the like). A trunk 406 interfaces to the switch404, and each voice server 402 is connected to the switch over anconnection such as ISDN Primary Rate Interface (PRI) line 408. Each ISDNPRI line 408 (and, thus, each voice server) handles up to twenty-three(23) calls in a representative embodiment. Preferably, the data centersuse different network service providers to guard against individualprovider outages. When a data center is unavailable, an AutomaticRouting Feature (ARF) automatically forwards the incoming call to anavailable data center. The data center is able to handle any audio callgenerated by an authorized subscriber. As noted above, the data centerneed not have prior knowledge of the event.

FIG. 5 illustrates a representative voice server 500. As noted above,there are preferably multiple voice servers at each data center. Thevoice server comprises commodity hardware 502 running an operatingsystem 504 such as Windows 2000 or Linux. An Internet audio conferencingcard 506, such as an Intel Dialogic DCB/SC Series card, an IntelDialogic DM/V-A Series card, or equivalent, is used to interface to theserver the incoming audio signal from the user. One or more encoder 508a-n provides format-specific encoding. Thus, a representative serverincludes a Real encoder, a Windows Media Server (WMS) encoder, and thelike. Typically, an encoder is implemented as computer software, i.e., aseries of code instructions. Preferably, an encoder process isinstantiated for each inbound call that is to be cast. An encoder isdisabled (i.e., stopped) and the event archived upon a given condition,e.g., the user going on-hook or entering a given keypad code such as399. In addition, the server 500 includes one or more applications thatare executable on the platform for the purposes to be described below.These applications include a voice server telephony engine (VSTE) 510,and a voice server network manager (VSNM) 512. These modules can beseparate or combined. The VSTE 510 performs a number of functionsincluding: handling call control and signaling (e.g., per the Q.931standard), providing an interface to the conferencing card 506 firmware,playing voice response files requesting eventID and PIN, decodingdual-tone multi-frequency (DTMF) responses from the user's telephonekeypad, recording digital audio files, publishing monitoring data tablesas will be described, and generating event logs.

FIG. 6 is a simplified flowchart of the operation of the voice serverupon initiation of a call. In particular, it is assumed that the eventhas been reserved using the Web-based reservation subsystem and that theincoming call has been directed to a given voice server in the datacenter. At step 600, the VSTE instructs the conferencing card to answerthe incoming call. At step 602, the VSTE issues voices promptsrequesting the user to enter the eventID and PIN. To authenticate thisinformation, the VSTE transfers control to the VSNM, which, at step 604,issues a request, e.g., via HTTP, to the content storage subsystem tofetch the event_info.xml file for the event. At step 606, theevent_info.xml file is returned to the VSTE. The routine then continuesat step 608 wherein the VSTE authenticates the event information, e.g.,by evaluating the status flag to ensure that the event is not alreadyover, and by verifying that the PIN returned in the event_info.xml filematches the PIN entered via DTMF by the user in response to the voiceprompts. If the event information is authenticated, the VSTE thencontinues at step 610 to instantiate the proper encoder (identified bythe format flag) to begin audio streaming of the event. This completesthe process.

According to a technical advantage of this invention, audio castingbegins whether or not the VSTE can establish a connection to the contentstorage subsystem and/or is able to receive or authenticate giveninformation in the event_info.xml file. In particular, preferably thePIN itself is self-checking and can be regenerated “on-the-fly” by theVSTE if the PIN in the event_info.xml file is unavailable for anyreason. A convenient technique to accomplish this is to generate the PIN(in the first instance) as a one-way hash of the eventID (or some otheridentifier) and a shared secret. As long as the VSTE knows or can obtainthe shared secret, it can regenerate the PIN and compare it to the codeentered by the user (e.g., via DTMF). Thus, there is no delay ininitiating the event if event_info.xml is not available to the VSTE inthe server.

As is well-known, streaming media delivery requires that a stream have agiven name. Typically, the stream name corresponds to some resource overwhich the stream is output. Conventionally, a resource is usually a“port,” a “publishing point,” or the stream is merely associated withsome unique name. In a representative embodiment, it is assumed that thevoice servers output streams on ports. This is not a limitation of theinvention, however. In this embodiment, another technical advantage isprovided by allocating or “pre-assigning” ports to each voice server inthe data center. Thus, for example, a first server in the data center isallocated ports 10,000 through 10,049, a second server is allocatedports 10,050-10,099, and so on. Preferably, the ports are allocatedduring set-up of the voice servers in the data center. The above portnumbers are merely representative. By pre-allocating ports on each voiceserver, there is no need for a particular server that will serve thestream to perform a database lookup to obtain a port number. As aconsequence, normal processing delays required for that operation areavoided. Pre-allocation can also be used where publishing points, uniquenames or other delivery techniques are applied to the server streams.For the sake of illustration only, a port-based solution is describedbelow.

It is assumed that the event is now being streamed on one of thepre-assigned ports. FIG. 7 is a flowchart illustrating how an audiencemember (an “attendee”) joins the audiocast. FIG. 8 illustrates variousprocesses that are used to implement this operation. At step 700, theattendee activates (by clicking a link or entering) the attendee URL ofthe form:

https://web.servicebureau.net/meta?event=<eventID>&format=<name>.

At step 702, the attendee's browser is directed to a given attendeeaccess subsystem (if more than one is running) using a traffic managerproduct, system or managed service as described above. With referencenow to FIGS. 7 and 8, a metafile generator 800 running in the attendeeaccess subsystem receives the client request and, in response, issues aport identification request to the monitoring data subsystem 802. Themetafile generator may be implemented as a servlet, a library, or anyother convenient mechanism. This is step 704, and the portidentification request typically identifies the eventID and the format.In return, the monitoring data subsystem returns the number of the porton which the event is being streamed. As noted above (where ports areused for streaming), a voice server streams a given call over a givenport identified by a port number. Each time a voice server starts anencoder instance, the voice server preferably generates a dataset, e.g.,{eventID, format, port #} for the stream being output from the port. Asnoted above, in certain circumstances (e.g., a bridged conference or ifmore than one data center is engaged for the event), a redundant calloccurs, in which case another voice server will be generating anotherdataset with the same eventID and format, but with a different port #(as all port numbers are pre-allocated and unique). Each dataset iscontinuously pushed to the monitoring data subsystem 802, whichpublishes to the voice servers a table 804 identifying the activeevents. Thus, at step 706, the monitoring data subsystem 802 returns tothe metafile generator 800 an identification of the port(s) (orpublishing point(s)) on which the stream(s) (as defined by the eventIDand format) are being delivered from the voice server(s). The routinethen continues at step 708, with the metafile generator 800 generating ametafile 806. Metafile 806 is a data structure that includes one or morestream Uniform Resource Locators at which the stream is available to theattendee's streaming media player. For each eventID and format pair,there is preferably one URL. The URL is provisioned with the appropriatestream format and other data necessary to enable the attendee'sstreaming media player to obtain the content. This URL is sometimesreferred to as a “stream URL” to distinguish it from the attendee URL.Thus, for example, a representative stream URL is of the followingformat (assuming a WMS stream made available on a delivery network named“reflector” and port 3012):

mms:// . . . stream.net/<cpcode>/<integritycheckdata>/reflector:3012.

If there are redundant streams, the metafile 806 will include a secondstream URL at which the stream can be obtained, e.g., as a fail-over ifthe stream is unavailable from the other stream URL. As can be seen,metafiles are generated dynamically based on the current state of theevent. The system also preferably enables a user to customize a metafilethrough static and/or dynamic XSL files. At step 710, the metafilegenerator 800 returns the metafile 806 to the attendee's web browser. Atstep 712, the attendee's web browser's media player is launched to thestream URL automatically to obtain the stream. If a connection can beestablished, the attendee is now participating in the conference.

It may be desirable (but not required) to authenticate an attendee priorto returning to the attendee's browser the stream URL. This may beaccomplished as follows. When the system generates an attendee URL for aspecific event, this URL preferably has the host or attendee's passwordembedded therein. As a consequence, the system can determine if thecorrect password is provided without having to do any lookups. Arepresentative URL is the following:

<unsigned part of URL>& . . . &<signed part of URL>& . . . &<signature>,where:

<unsigned part of URL>=given information;

<signed part of URL>= . . .&org_idxxx&event_id=yyy&event_time=zzz&MD5(attendee/host_pw,org_id);

<signature>=MD5(<signed part of URL>, secret key).

Note that even though event_time (and probably other information) isincluded in the URL, this information is only used to facilitate theevent if the content storage subsystem (and, thus, the event_info.xmlfile) is unavailable. The most up-to-date information preferably islocated in the event information file in the storage subsystem. If theMD5 hash value matches the value in the signed portion of the URL, theattendee is authenticated to attend the conference.

One of ordinary skill in the art will appreciate from the abovediscussion that the inventive conference system provides fully-automatedtelephone signal acquisition and streaming in addition to the JITreservation provisioning. The system authenticates the eventautomatically (even if access to the reservation information inevent_info.xml is unavailable), starts up the encoder, and injects thestream into a delivery network as soon as the user begins speaking.Stated another way, all the user has to do is dial the conferencesystem, enter the eventID and PIN, and begin the call. The telephonesignal (i.e., the conference call) is immediately available toprospective attendees, who access the call by simply activating theattendee URL that has been provided to them following reservation. Inresponse, the attendee access subsystem returns (to the requestingclients) metafiles that include the stream URL to which the attendeestreaming media players are automatically directed.

The conference system of the present invention also provides enhancingarchiving capabilities as compared to the prior art. As described above,the archive subsystem preferably operates at different data centerlocations, in which case a particular archive subsystem is reachedthrough a traffic manager. In an illustrative embodiment, an archivesubsystem comprises an archive process 808. When the archive subsystemis mirrored, this process runs on one or more machines. Preferably, eachevent gets archived when the event is over, which may be indicateddirectly (with the user entering a given code such 399) or indirectly(when the user disconnects the call and an archive timeout expires). Aswill be described below, the mere termination of the call connectiondoes not always reflect that the event is actually over although, in thepreferred embodiment, the termination of a call does generate an upload(from the voice server to a given content storage subsystem) of a filerepresenting the stream. Thus, typically a given event is captured inmore than one stream and, thus, more than one associated file upload tothe content storage subsystem. As used herein, archival preferablyoccurs with respect to the overall event itself and thus typicallyinvolves processing (e.g., aggregation, partial substitution, or thelike) of the upload files representing the event.

In a distributed system, there are typically several archive processesrunning at the same time. One archive process preferably is elected as aso-called “leader.” The archive process gets required information fromthe monitoring data subsystem and examines the stream historyinformation. Any convenient leader election protocol may be used. Thus,for example, a given archive process announces a subscription list toall other archive processes and listen for the lists from otherprocesses. The process then merges together the lists received from theother archive processes and elects a leader by the following: sort thelist of responses by IP address, remove any machines that have not beenheard from over a given period (e.g., 20 seconds), select a givenmachine as the leader, and notify the other machines.

FIG. 9 is a flowchart illustrating a preferred archival operation. Theroutine assumes that an event is in process. This implies that one ormore voice servers are outputting streams. At step 900, as the event isstreamed, an encoder of a voice server (that is actively streaming theevent) writes the stream to its local disk. At step 902, a determinationis made if the audio signal being processed by the voice server has beeninterrupted. If not, the routine cycles. If, however, the audio signalbeing processed by the voice server has been interrupted, the processcontinues at step 904 with the VSNM performing an upload (preferably byFTP) into the <eventID>directory on the content storage subsystem. Ifthe <eventID>directory has been mirrored, the traffic manager may beused to select an optimal mirror site for the upload. The file upload,however, does not necessarily mean that the event is over. Thus, a testis performed at step 908 to determine if another voice server isoutputting a stream for the event. The leader can determine this fromdata supplied by the monitoring data subsystem, which identifies whichvoice server(s) are outputting streams for the event (and on whichports). If another voice server is outputting a stream for the event,the routine returns to step 900. If, however, the outcome of the test atstep 908 is negative, a test is performed at step 910 to determinewhether a given timeout has expired or the host has entered a given code(e.g., 399). If not, the routine cycles to step 908. If the timeout hasexpired or the access code entered, the event is considered over andprocessing continues at step 911 to begin the archival process. Inparticular, at step 911, the archive leader process edits theevent_info.xml file to reflect that the event has ended and to log dataabout the event. Thus, for example, the archive process alters thestatus flag, identifies the stream start time, the stream end time, theunique filename(s) provided by the voice server(s) during the FTPupload(s), and the like. At step 912, the archive leader processesstream(s) associated with the event to generate the archive. At step914, the archive is stored in the event_info.xml directory. At step 916,the archive is replicated to any mirror. Step 916 is optional. Thiscompletes the automated archive operation. Once this operation iscomplete, an end user can point his or her browser to the system andobtain the archive of the event for the period originally specified inthe reservation. Preferably, the archive is obtained by having an enduser who desires the archive open his or her browser to the attendee URLto obtain the metafile (and the embedded stream URL) in the mannerpreviously described.

The processing of streams in step 912 is now described. As noted above,there are several circumstances in which multiple streams are generatedduring an event. In one case, the host dials-in to two separate datacenters (over two separate telephone numbers) to initiate multiplestreams (from two different voice servers) for redundancy. A bridgedconference call can create multiple streams from two voice servers. Inanother common scenario, the user terminates the conference prematurelyor inadvertently (e.g., by disconnecting the call). The call is thenlater restarted over a different stream by a different encoder but withthe same eventID and PIN (and, thus, the same event_info.xml file). Inall such circumstances, it is desired for the archive subsystem to beable to construct an archive version of the overall event. In some cases(e.g., where a single call is dropped) this requires that multiplestreams (perhaps from different data centers) be concatenated together.In other cases (e.g., where there are multiple streams), it may bedesirable to use a portion of one stream for one section of the call anda portion of another stream due to quality or other considerations.Thus, in accordance with the present invention, when the archive leaderprocesses the streams in step 912, such processing typically includesthe generation of given metadata that identifies which portions of eachstream should be played and in what order to create the archive. Thismetadata is stored in the event_info.xml file during step 914.Preferably, the raw data uploaded from the voice servers is storedunmodified, and the metadata is used during replay of the archive. Inthis sense, the event_info.xml file stores a “virtual” archive. Thus,e.g., the metadata for a particular call may instruct the end user'smedia player to play stream 1 “starting at time x and ending at time y,”then play stream 2, and so on. The “starting at time x and ending attime y” information is the metadata.

Generalizing, there are many cases where there are multiple streams(with each stream representing an event fragment) for a given eventprovided to the archive leader process. In the simple case, the archiveleader process analyzes the start and end times of the streams and, ifappropriate, instructs the streaming media player requesting the archiveto merely concatenate the streams together. Where streams overlap intime but come from different voice servers, the archive leaderidentifies the appropriate stream fragments and stores the associatedmetadata in the event_info.xml file to control how the multiple streamsare played on a requesting streaming media player.

The archival process of the invention preferably occurs in afully-automated manner. In particular, each event preferably getsarchived when the user disconnects the call and an archive timeoutexpires or the event ends, e.g., by the user entering a given code.There may be several archive processes running at the same time, andtypically one archive process is elected as a leader. The archiveprocess gets required information from the monitoring data subsystem andexamines the stream history information. All the encoded files from allcalls are assumed to be in the content storage subsystem (they areplaced there by the voice servers, as described above). The archiveleader (if one exists) determines whether one or more of these filesmake an acceptable archive. As noted above, if there is an acceptablearchive, the archive process creates an ordered list of good file namesof the files placed in the content storage subsystem and writes thatlist in the event_info.xml file for that event. As also noted, the listincludes metadata about which portions of each stream should be playedand in what order to create an optimal archive of the event. If anacceptable archive cannot be determined, the archive process sets up anerror flag and stops monitoring the event. If this error flag is latercleared, then the archive process re-tries to archive the event.

The conference call is streamed over a delivery network in a preferredembodiment. As is well known, content delivery networks provide enhancedcontent delivery network by routing requesting clients to optimal oftenedge-based content servers which are not overloaded and that are likelyto provide access to the content. A representative streaming mediacontent delivery network is FreeFlow Streaming, available from AkamaiTechnologies, Inc. of Cambridge, Mass. In this technique, the stream issent on multiple redundant paths to enable a given edge server toconstruct a clean copy of the stream when some of the networktransmission paths are down or lossy. This “reflector” transport networkis described, for example, in U.S. Pat. No. 6,928,815.

FIG. 10 is a representative reflector network. In this example, thestream output from the voice server is sent to a content deliverynetwork (CDN) entry point 1202. An entry point, for example, comprisestwo servers (for redundancy), and each server can handle many streamsfrom multiple voice servers. Once the entry point receives the stream,it rebroadcasts copies of the stream to so-called set reflectors 1204a-n. A set reflector is a server. The streams are multiplexed anddelivered to the set reflectors preferably via UDP (e.g., WMTencapsulated in RTSP encapsulated in UDP over IP). These set reflectorsare preferably diverse from a network and geographic standpoint (e.g.,at diverse Internet backbone data centers) to ensure fault tolerance.Each set reflector, in turn, rebroadcasts its copy of the stream to eachsubscribing region, e.g., region 1206 d, of a set of regions 1206 a-n. Asubscribing region 1206 d is a CDN region that contains one or morestreaming edge nodes 1208 a-n to which user(s) have been routed by a CDNrequest-routing mechanism. In other words, set reflectors send theirstreams to every edge region where they are needed. A CDN region, inthis example, includes a set of edge nodes connected by a commonbackbone 1209, e.g., a local area network (LAN). Typically, an edgenode, e.g., node 1208 d, comprises a streaming server 1212 and it mayinclude a cache 1210. A representative server runs an Intel processor,the Linux operating system and a Real Media or QuickTime Server. ForWindows-based platforms, a representative server runs an Intelprocessor, Windows NT or 2000, and a Windows Media Server. The edge nodemay also run a control program 1214 to enable a given edge server tosubscribe to a given stream, which will occur when a conferenceattendee's streaming media player is directed to that edge server. Anillustrative request routing mechanism for resolving the stream URL toan optimal edge server for a given attendee is described in U.S. Pat.No. 6,108,703.

The content delivery network illustrated above is merely exemplary.There is no requirement that streams be delivered over this type ofreflector topology. In a simple implementation, the streams are outputon conventional WMS (or Real, Quicktime, or other format) publishingpoints and delivered to corresponding WMS (or Real, Quicktime, or otherformat) streaming servers over any type of network connection (e.g., theInternet, an enterprise-based intranet, a private network, VPN, or thelike).

The present invention may be operated as a managed service by a serviceprovider or made available as a standalone system. The system mayinclude an application programming interface (API) over which thirdparties can send messages (preferably XML) through a secure link (suchas HTTPS) to reserve, modify or cancel an event, or to get informationabout existing events. The system may also include an event manager toolthat is implemented as a Web-based extranet application. All nativeconference events can be monitored through this tool.

The following are additional details for a preferred embodiment of thevoice server. Preferably, the VSTE 510 supports B-Channel AvailabilitySignaling (BCAS) between the network switch over which the call isproceeding and the voice server. BCAS provides additional functionalityto allow load distribution across multiple voice servers, placingchannels out of service when a pool of available ports is low, allowingthe voice server to be suspended for maintenance, and providing theability to monitor PRI signaling or equipment failures. In particular,BCAS provides for initiation and acknowledgement of service requests toplace individual channels into one of three states: in service,maintenance, and out-of-service.

The VSTE 510 preferably also provides a so-called “port availabilitysuspend” function. This function removes all available channels fromservice when a pool of available ports on the voice server is low. Thisfunction prevents additional calls from being routed to the voice serverwhen there is a risk that encoder ports will not be available to streamthe event. When activated, any channel waiting for a call is placedout-of-service. As each event ends, the channel on which the event wasreceived is placed out-of-service. Port availability suspend isimplemented to prevent users from gaining access to unauthorized events.In operation, each user accessing an event stream receives anauthentication code, which is preferably valid for an authenticationcode timeout period. If the user accesses an event near its end, theauthentication code would be valid for the authentication code timeoutperiod, allowing the user to access another event on that port. This isundesirable. For this reason, the port on which the event is streamed isnot used again until after a “port reuse timeout period.” If the portreuse timeout is equal to or greater than the authentication codetimeout period, no user can access an unauthorized event. A voice serverpreferably is placed in port availability suspend mode when then voiceserver nears the point of no useable ports being available. When this“low port availability” condition is removed, channels are placed in an“in-service” condition.

The voice server 500 also can be placed in a suspended state formaintenance. In this state, all unused channels are maintained“out-of-service.” All busy channels are placed “out-of-service” afterthe event has been completed. When all events on a suspended voiceserver are out-of-service, PRI services (to the conferencing cards) aresuspended, and communications between the network switch and the voiceserver are terminated, thereby allowing the network switch to routecalls to other voice servers in the data center. The VSTE can alsodetect failure of d-channel communications and signaling errors.

As described above, each voice server includes one or morePRI-compatible conferencing cards. Although not illustrated, each voiceserver may be connected to the network switch either through a ChannelService Unit (CSU) or directly to the switch or other termination devicesupplied by a telecommunications service provider. Preferably, eachconferencing card is provisioned with its own d-channel, which enableseach voice server to maintain independent operation. Whether a CSU isrequired depends on the location of the network switch (5ESS, DMS 100,or the like) and on the termination equipment at the main point of entryat the data center. If the network switch is co-located with the voiceserver equipment, a T1 cable can be run between racks and a CSU is notnecessary. A CSU is also not required if the network switch is in aremote central office (CO) and termination equipment is available at thedata center through which the service provider can providediagnostic/loopback functions. A CSU may be used when there is no othermeans of verifying the connection from a remotely located network switchto the data center.

Preferably, the network switch provides the capability for acknowledgingservice messages sent from the voice server conferencing cards. Thisfeature is called “B-channel Availability Signaling” on the AT&T 5ESSswitch. The same feature set is referred to as “Remote Blocking” on theDMS-100 switch. The operation of service message signaling may be asfollows: service messages allow the customer termination equipment (inthis case, the conferencing card) to place individual bearer channels inand out of service. This functionality enables the port re-use, voiceserver suspend and load distribution functions. The conferencing cardsends a service message on the d-channel to a network switch requestingthat a channel be put in or out of service. The switch must thenacknowledge the service request. If the request was to put a specificchannel out of service, the network switch must acknowledge the servicemessage and then not route any calls to that channel. Preferably, callsare routed to the first available channel that is not out of service. Ifall channels of a conferencing card are either busy or out of service,the network switch preferably routes calls to the next available card.

In summary, the inventive system does not require that physicalresources be reserved ahead of time. An event can be reserved and thenexecuted at any time, and all physical resources preferably areallocated to the event in a “just-in-time” (JIT), on-demand fashion.This provides significant flexibility and reduced costs as compared toprior systems. More specifically, the system of the invention does notpre-provision any audio resources. Rather, substantially all audioresources are bound to the event upon user call-in. These resourcesinclude the data center, voice server and the encoder. This“just-in-time” or on-demand allocation of audio resources enables thesystem to become more fault-tolerant. Any resource or asset that fails,prior to signal acquisition, results in the removal of that equipmentfrom an available resource pool. This allows the system to choose amongassets that are available and in working order. To ensure that the stateof these assets is correct, the system implements automatic monitoringand testing of resource assets. A dial-in results in the conferenceusing only audio resources that are working, thus maximizing faulttolerance. After the user logs in and is connected to a voice server,the system does not rely on a database to execute the event. Thedatabase interface of the system preferably is asynchronous such that ifthe database is unavailable at the time a request for an eventreservation is made, the reservation completes as required. Later, thedatabase is updated with the reservation information.

The archiving process for audio provides a great deal of flexibilitythat is used to manipulate when an archive is produced, when it isusable by the audience, and how dropped calls are handled. As described,the system automatically archives an event after it has ended or a callback period has expired. An archive is generated when the event is knownto be over or after the event the systems has detected that, for somefixed amount of time, no live streams are being generated. Via a webinterface or via DTMF (for audio), a host can notify the system that theevent is over, and in this case, an archive is generated right away.There will be separate timeouts to determine when an event is over andwhen an event should be archived. When an event is over, no calls forthat event will be accepted at the voice servers. Archive timerspreferably are initiated after a customer hangs up or the call drops.Preferably, this timer is set at a given default for all events or canbe set on an individual basis. After the timer expires the file isuploaded to storage. Users of the system have their conference eventfiles uploaded to a designated FTP directory. After the upload, thecontent storage system preferably replicates the content, placing copiesof the files on each of multiple storage centers.

When an end-user requests an archived event that is not already cachedin the streaming server determined optimal for the end-user, the serverfetches a copy of the requested file from the optimal storage center.One technique for accomplishing this is described in U.S. PublicationNo. 2002/0143888. Then the streaming server fulfills the user's requestand also keeps a copy of the file in its cache so that it can fulfillsubsequent similar requests for that content.

The present invention provides a distributed, standards-based softwarearchitecture that provides a comprehensive set of functionality forinteractive communication services and is designed for maximumscalability and reliability. The platform enables robust eventprovisioning, signal acquisition, monitoring, archiving, reporting andbilling required for base streaming. The inventive functionality in madeavailable from an applications platform rather than a one-size fits-allapplication. Service providers can provide an integrated and customizedproduct through use of the APIs, and even integrate their own technologyas desired. As noted above, a significant advantage of the invention isthat it does not require that physical resources be reserved ahead oftime. An event can be reserved and then executed right away, and allphysical resources are allocated to an event in a “just-in-time,”on-demand fashion. The system has no single points of failure, and it isself-healing. That is, no single component failure can bring down anevent, and when a component does fail, the system compensatesautomatically. In addition, the system is able to handle large numbersof simultaneous events and massive total audience sizes. As demandgrows, the system can easily be expanded to accommodate the load.

1. Apparatus for web casting over a computer network, comprising: afirst subsystem accessible over a computer network and including codefor enabling a reservation entity to reserve a web casting event, toobtain an event identifier, an access code, and an attendee URL, and toinitiate storage of an event information file associated with the webcasting event, where the web casting event is a web-based audioconference event for casting speech of a speaker to one or more audiencemembers over the computer network; a second subsystem including code forenabling initiation of the web casting event by entering the eventidentifier and access code, and code for generating a data stream froman audio signal derived from speech of a speaker, wherein the speech ofthe speaker is receivable by the second subsystem over a telephonenetwork; and a third subsystem accessible over the computer network andincluding code responsive to a client browser associated with alistener, who is an audience member, requesting the attendee URL forreturning to the client browser a data structure including a stream URL,wherein the stream URL enables a streaming media player to obtain thedata stream so that the listener can hear the speaker during theweb-based casting event; a fourth subsystem accessible over the computernetwork and including code for generating a directory for the webcasting event, and code for storing in the directory the eventinformation file and the uploaded data stream; and a fifth subsystemaccessible over the computer network and including code for creating anarchive of the web casting event and for storing the archive in thedirectory.
 2. The apparatus as described in claim 1 wherein the secondsubsystem comprises a set of one or more servers, wherein each of theservers includes a telephone control engine for playing voice promptsrequesting entry by the speaker of the event identifier and the accesscode.
 3. The apparatus as described in claim 2 wherein the telephonecontrol engine writes the data stream to a storage disk associated withthe voice server during the web casting event.
 4. The apparatus asdescribed in claim 3 wherein the telephone control engine uploads thedata stream from the storage disk if the audio signal is interrupted. 5.A method of web casting, comprising: reserving a web casting event (a)by providing a reservation entity with an event identifier, access codeand attendee URL; (b) generating an event information file, and (c)creating a directory associated with the web casting event in which theevent information file is stored, wherein the web casting event is anaudio conference casting event; initiating the web casting event (a) byverifying that an access code entered by a host is a given function ofthe event identifier entered by the host, and (b) upon verification,encoding speech data derived from speech of a speaker into a datastream; enabling a listener, who is an audience member, to access thedata stream (a) by returning to a client browser launched to theattendee URL a data structure including a stream URL at which the datastream can be obtained so that the listener can hear the speaker duringthe web casting event; and generating an archive upon completion of theweb casting event.
 6. The method as described in claim 5 furtherincluding: generating a copy of the data stream as the web casting eventproceeds; and automatically uploading the copy to a central store if theencoded speech data is interrupted.
 7. The method as described in claim5 wherein the step of generating the archive includes: defining metadatafor each data stream copy that defines what portion of each data streamis to be used for the archive; and storing the data stream copies andthe metadata in a directory of the central store uniquely associatedwith the event identifier.
 8. The method as described in claim 5 furtherincluding the step of enabling access to the archive upon entry of theattendee URL.
 9. The method as described in claim 5 further including:restricting access to the archive after a given time period has elapsedas determined by information in the event information file.
 10. Themethod as described in claim 5 wherein the data streams are streamedover a content delivery network.